Back to Blog

Tim Gemoll · 2026-07-21

"Your Business 'Has AI.' But Who's Doing the Work?"

"Your Business 'Has AI.' But Who's Doing the Work?"

I keep coming back to a pattern I see in nearly every business I talk to.

They tell me they're using AI. And they are - technically. Someone has a ChatGPT tab open. Maybe two or three people do. They type something in, get an answer, copy it somewhere, move on. The tool works fine.

But the business isn't really using AI. One person is.

And when that person is slammed, out sick, or leaves - the AI usage stops. The prompts they figured out? Gone. The context they built up over weeks of conversations? Wiped when the chat window got too long and the results started getting weird.

This is what "AI adoption" looks like for most businesses right now: individual, manual, copy-paste, and completely non-durable.


The tab problem

Here's what I mean.

A browser tab that only works when you're the trigger. You have to open it, type the right thing, wait, copy the output, and paste it somewhere else. It has no memory of what you were doing yesterday. The chat fills up and the results drift. And the great prompt someone figured out last month? It lives in their personal account. Nobody else knows it exists.

That's not a tool problem. ChatGPT and Claude are genuinely good. The pattern is the problem.

When AI only works because one specific person started it, nothing is repeatable. When the results depend on who asked and how they asked it that day, nothing is consistent. And when the knowledge of how to get good results lives inside one person's head and their browser history - that's not operational capacity. It's a single point of failure.


Why most AI usage doesn't show up in results

There's a reason that most companies say they're using AI, but struggle to point to actual results from it. McKinsey's March 2025 data found that more than 80% of organizations reported no measurable business impact from their AI efforts. That's not because the tools are bad. It's because most usage looks like what I just described — individual, ad-hoc, non-repeatable.

You can't build on a foundation that resets every time someone closes a tab.


The fix is simpler than you think

A consistent, documented system prompt.

That's it. Not a new tool. Not a platform migration. Not a six-month implementation project. One document that defines, for a specific role or workflow, what this AI is supposed to do, how it should respond, what context it always needs, and what it should never do.

When the system prompt is in place:

  • Anyone on your team can get the same quality of output — not just the person who figured out the right way to ask
  • Results are consistent whether it's Monday morning or Friday afternoon
  • Onboarding a new person means handing them the document, not hoping they figure it out over six weeks
  • The knowledge lives in your business, not in someone's personal browser history

This isn't complicated. It's just a different way of thinking about the setup. Most people skip it because nobody told them it mattered.


What I put together

I made a Google Doc I'll send to anyone who wants it. It has two things:

  1. A prompt you can use to generate a system prompt for your specific role or workflow — the AI helps you build it
  2. An implementation prompt so the AI walks you through setting it up

You don't need to know anything about how these tools work under the hood. You just need the doc and about thirty minutes.

It's not a sales pitch for anything. I put it together because this is the one change that moves people from chatting with AI to actually using it — and I'd rather just give it away than watch another business restart from zero every time someone logs out.

If you want it, email me at tim@t2coders.com. I'll send it back the same day.

No form. No funnel. Just the doc.



Sources

  • "McKinsey & Company, The State of AI in Early 2025, March 2025 — 80%+ of organizations report no measurable EBIT impact from AI deployment"